feat: support multiple versions of the pg-safeupdate extension #1871
+217
−22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jfroche
force-pushed
the
multi-version-ext/pg_safeupdate
branch
2 times, most recently
from
5ff6e64 to
fc06be9
Compare
Build multiple versions of the pg-safeupdate extension on different PostgreSQL versions. Add test for the extension and their upgrade on PostgreSQL 15 and 17.
yvan-sraka
force-pushed
the
multi-version-ext/pg_safeupdate
branch
from
631ced6 to
c377e28
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Build multiple versions of the pg-safeupdate extension on different PostgreSQL versions.
Add test for the extension and their upgrade on PostgreSQL 15 and 17.